 
Install notes
 
For Android: 
 
Extract the 'Qnect.apk' file from the 'Qnect_beta_0.1.2_Android.zip' file to a folder on your Android device, locate the file and tap on it. When prompted choose to install the app, the old version will automatically be overwritten. All of your cached date will remain on the device, your cached data (chat history, encountered users, groups, nodes statistics, log, API calls log, etc..) will only be deleted if you explicitly do so through the app cache menu or if you remove Qnect from your device.

For Linux:

Delete you old 'Qnect' folder from the location where you previously extracted it to. Extract the new 'Qnect' folder from the 'Qnect_beta_0.1.2_Linux.zip' file to your preferred location, go into the folder and give the 'qnect' file permission to run as an executable (if necessary), then double click that file to start the app. All of your cached date will remain in your Linux Documents folder, your cached data (chat history, encountered users, groups, nodes statistics, log, API calls log, etc..) will only be deleted if you explicitly do so through the app cache menu or if you delete the 'Documents/Qnect' folder or its content from your operating system file manager.


Qnect 0.1.2 release notes


New:

- Added private nodes option. You can now keep and edit a list of URL's for your private node(s). Qnect will always prefer to use private nodes first if they are available and if that option is enabled. If Qnect fails to make an API call to all of the private nodes on your list it will fall back to using the public nodes, but only if you have enabled the use of public nodes. You will see a warning in the top bar of the app if Qnect fails to make an API call through your private node but succeeded making it with the public nodes. Learn more about setting up your private node on the Qnect QDN website or at https://qortal.link/Qnect/private-nodes-setup.

- Logging is now disabled by default (only for fresh installs).

- Mouse cursor now indicates that the image for link preview is clickable (suggested by Leiff)

- Changed pop-up dialog when clicking up and down buttons in chat screen to 'slide down bar' at the top of the screen. This seems to be a lot less intrusive and improves user experience, user feedback would be appreciated. (changed due to a suggestion by mrhelloyellow)

- Added api.qortal.org to the default public nodes list (thanks to crowetic). If you already had Qnect installed and want to make use of this node you'll need to manually add this URL to your public nodes list or reset that list to default which will reset your list to the hard-coded new list including the new node.

- Added an algorithm which checks for messages that were missed in previous API calls. Previously, Qnect would not query the API for messages older than the last stored message in a group. The assumption is that the missing messages could have an older timestamp than the last stored message but were missing in a previous API response. Qnect will now look for all messages from the last 4 hours and only add the ones which do not yet exist in your local chat history. If a message is found with an older timestamp, it will not be placed in its correct chronological position in the chat history but at the current index, this is to give the user a visual indication that a message was found which was missing in a previous API response. In the future (if this algorithm does not become obsolete) the previously missing message will be placed at the correct index.


Fixed:

- Nodes that fail to return a response will no longer be put on the 5 minute time-out list. A failed response is likely the result of an API call to a non-existing resource (usually a non-existing avatar) so there's no need to temporarily blacklist the node. Nodes that take too long to respond will still be placed on the time-out list for 5 minutes.

- Settings set in the main menu (on the right) and connections menu (on the left) were only being saved after closing the menu, this could result in your settings not getting saved when you close the app while the menu is still open. All settings except for settings set through sliders (chat pagination section) will be saved upon changing the value. The chat pagination settings still require closing the menu in order to be saved.

- Failed avatar lookups will no longer cause a 'lost connection' notification. A missing avatar is not neccisarily due to connectivity issues, in many cased the user may just not have set an avatar.

